You can route gate receivals for pre-advised containers to the N4 XD Service instead of to XPS. Doing this removes the load off the XPS server for mega terminals with huge gate traffic. This supports the following gate processes:
Gate Receival
Direct Gate Receival to Vessel and Rail
Gate Flip (for default flip functionality)
Supported for Pre-advised containers only
How it works:
Set the N4 setting ROADGATE037 to XD.
Turn on the XPS privilege XDSRVC (on page 1) on the XPS client that is designated to run as the N4 XD Server. In the N4 Cluster Services view, the Type column displays XD Service and the Status column displays Active.
Enter a gate receival for a pre-advise container using the Gate form.
The XD Load Balancer forwards the XD gate decking Bento request SCALED_XD_ADVISE_UNIT_REQUEST to the N4 XD Client.
The XD Client processes the request, returns a valid yard position to N4, and creates the work instruction (WI).
The Decking History view in N4 displays the decking request. The Decking Type column displays XD Advise Unit and the Node column displays the XPS client designated to run as the N4 XD Server.
The Maintain Queues window in XPS displays the WI created by the N4 XD Service. The From attribute displays TQ and To attribute displays the the yard block.
After completing the yard stage, the From attribute displays TIP and To attribute displays the the yard block.
Note the following:
When you enter a gate recevial for a pre-advised container with ROADGATE037=XD and the XDSRVC=ON, N4 bypasses the call to the XD Server and the XPS server completes the decking. The Decking Type column displays XD Advise Unit and the Node column displays the XPS server address in the Decking History view.
When you enter a gate recevial for a pre-advised container with ROADGATE037=XD and the XDSRVC=ON, and if the XPS client designated as the <xd> server freezes, the XPS server completes the decking.
If the XPS client designated as the <xd> server cannot be connected to, the Status column displays 'INACTIVE' in the Cluster Services view.
If you use a Scaled N4 XD service, the N4 setting ARGOXPS006 (XPS_SOCKET_TIMEOUT) (on page 1) specifies the time (in seconds) for which N4 must wait for the vessel discharge and gate receival decking Bento response from a N4 XD server or the XPS server. If there is a XD client Bento timeout or XD client Bento connection failure, the Bento request is bypassed to the XPS server based on the timeout value defined for the setting.
If you set ARGOBENTO002 (on page 1) to either XPS_SERVER_WITH_XD or N4, N4 uses the same XD node for both vessel discharging and gate receivals. You cannot designate two XD nodes, one each for vessel discharge and gate receivals.